⚠️ No Changeset found

Latest commit: a222dee

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

🔵 Tier 2 — Low Risk

Small, isolated change with no API route or data model modifications.

Review process: AI review + quick human skim (target: 5–15 min). Reviewer validates AI assessment and checks for domain-specific concerns.
SLA: Resolve within 4 business hours.

To override this classification, remove the review/tier-2 label and apply a different review/tier-* label. Manual overrides are preserved on subsequent pushes.

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	Apr 9, 2026 7:02pm

PR Review

• ⚠️ Suppress comments use potentially non-standard rule names (react-hooks/refs, react-hooks/immutability, react-hooks/use-memo) — the standard eslint-plugin-react-hooks rules are only rules-of-hooks, exhaustive-deps, set-state-in-effect, set-state-in-render. If these are v7 additions, it's fine; if not, the comments are no-ops (the lines would still violate the equivalent @eslint-react rules, which are already disabled in config). Verify these rule names are real by running npx eslint --print-config on one of the affected files and checking if react-hooks/refs appears.

• ⚠️ Some disabled @eslint-react rules lack direct react-hooks equivalents: @eslint-react/no-nested-component-definitions, @eslint-react/error-boundaries, @eslint-react/purity, @eslint-react/unsupported-syntax — the comment says "equivalent rules enabled in eslint-plugin-react-hooks" but these aren't duplicates of any standard react-hooks rule. If these were active in recommended-type-checked, they'll now go unenforced. Worth confirming these were also inactive under the old recommended + disable-conflict setup.

✅ No critical bugs or security issues. Config change is transparent and intentional; suppression patterns on useStableCallback, usePrevious, and RAF ref mutations are all well-known valid exceptions.

E2E Test Results

✅ All tests passed • 130 passed • 3 skipped • 1083s

Tests ran across 4 shards in parallel.

View full report →